Skip to content

fix: reject boolean progress totals - #3219

Closed
iamdhrv wants to merge 1 commit into
modelcontextprotocol:mainfrom
iamdhrv:agent/reject-boolean-progress-total
Closed

fix: reject boolean progress totals#3219
iamdhrv wants to merge 1 commit into
modelcontextprotocol:mainfrom
iamdhrv:agent/reject-boolean-progress-total

Conversation

@iamdhrv

@iamdhrv iamdhrv commented Jul 30, 2026

Copy link
Copy Markdown

Summary

  • treat a boolean total in an inbound progress notification as absent
  • preserve delivery of the otherwise valid progress notification
  • extend malformed-wire regression coverage to distinguish booleans from numeric values

Fixes #3217.

Validation

  • ./scripts/test (5580 passed, 10 skipped, 1 xfailed, 100% coverage)
  • uv run --frozen pytest tests/shared/test_jsonrpc_dispatcher.py -q (79 passed)
  • uv run --frozen ruff check src/mcp/shared/jsonrpc_dispatcher.py tests/shared/test_jsonrpc_dispatcher.py
  • uv run --frozen ruff format --check src/mcp/shared/jsonrpc_dispatcher.py tests/shared/test_jsonrpc_dispatcher.py

AI assistance was used during implementation. I reviewed the resulting code and tests and take responsibility for the contribution.

Signed-off-by: Dhruv Maniya <dhruvmaniya1998@gmail.com>
@maxisbey

Copy link
Copy Markdown
Contributor

Thanks for putting this together. Closing along with #3217 — the reasoning is over there: nothing real emits a boolean total, so we're not going to special-case it on the receive side.

@maxisbey maxisbey closed this Aug 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[v2] Boolean progress total is delivered to callbacks as 1.0

2 participants